home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Amiga Format CD 48
/
Amiga Format CD48 (1999-12-13)(Future Publishing)(GB)(Track 1 of 2)[!][issue 2000-01].iso
/
-in_the_mag-
/
networking
/
crosspc
/
parpc04
/
packet
/
docs
/
install.doc
< prev
next >
Wrap
Text File
|
1993-08-12
|
9KB
|
255 lines
August 12, 1993
Installation instructions for the packet driver collection
(Currently only for PARnet & SLIP)
Document conventions
All numbers in this document are given in C-style
representation. Decimal is expressed as 11, hexadecimal is
expressed as 0x0B, octal is expressed as 013. All reference to
network hardware addresses (source, destination and multicast)
and demultiplexing information for the packet headers assumes
they are represented as they would be in a MAC-level packet
header being passed to the send_pkt() function.
Using the packet drivers
The packet driver must be installed prior to use. Since
each packet driver takes only a few thousand bytes, this is best
done in your autoexec.bat. Since the Ethernet boards typically
have jumpers on board, the packet driver must be informed of the
values of these jumpers (auto-configure is possible, but can
disturb other boards). The first parameter is the software
interrupt used to communicate with the packet driver. And
again, because each board is different, the rest of the
parameters will be different.
All parameters must be specified in C-style representation.
Decimal is expressed as 11, hexadecimal is expressed as 0x0B,
octal is expressed as 013. Any numbers that the packet driver
prints will be in the same notation.
Before installing the packet driver, you must choose a software
interrupt number in the range between 0x60 and 0x80. Some of
these interrupts are used for other purposes, so your first
choice may not work. See Appendix A for the section of Ralf
Brown's interrupt list between 0x60 and 0x80.
Running a packet driver with no specifications will give a
usage message. The parameters for each packet driver are
documented below.
Most drivers can also be used in a PROM boot environment, see
PROMBOOT.NOT for how to use -d and -n options for that purpose.
The -w switch is used for Windows. Install the packet driver
before running MS-Windows. This switch does not prevent Windows
from swapping your network application out of memory, it simply
detects when that has happened, and drops the packets on the
floor.
PARNET
usage: PARNET [-n] [-d] [-w] <packet_int_no> <int_level>
<io_addr> <netaddr>
The PARNET driver is an Ethernet adapter simulation for
PARnet-PC. PARNET-PC is a direct port from the Amiga's PARnet
PARnet which enables a multi-host network on one parallel line.
However, since not all parallel (printer) cards don't support
bi-directional pulled-up centronic cable, you must have a PARnet
INTERFACE. A description of this interface is given in the
PARPCXX.ZIP file in which XX represents the version number.
The parameters are as follows. The INT_LEVEL is the hardware IRQ
on which your parallel card is connected. In 99% of the cases
this is IRQ7 (enter: 7). The IO_ADDR is the portaddress of the
card, in standard configurations this is 0x378 (LPT1) or 0x278
(LPT2). The NETADDR is the PARnet address of this interface, this
is an unique number for each interface. You can choose any number
inbetween 0x01 and 0xfe (1 to 254 decimal). NOTE: When sending IP
packets, the driver uses the last octet in the IP addresses to
reach other hosts. So when you already have a fixed IP address for
your machine, let NETADDR be the last number. (e.g. when you have
the address 193.79.1.2, the NETADDR MUST be 2! ).
^ ^
SLIP8250
usage: SLIP8250 [-n] [-d] [-w] packet_int_no [-h]
[driver_class] [int_no]
[io_addr] [baud_rate] [recv_buf_size]
The driver_class should be SLIP, KISS, AX.25, or a
number.
The SLIP8250 driver is not strictly an Ethernet adapter,
however some software packages (such as KA9Q's NET and NCSA
Telnet) support Serial Line IP (SLIP). SLIP must be specially
supported because it doesn't use ARP and has no hardware
addresses prepended to its packets. The PDS is not clear on
this, but the packet driver does the SLIP encoding.
The parameters are as follows. The -h flag is included if you
wish to use hardware handshaking (the packet driver will then
suspend the transmission of characters while CTS is low). The
driver_class is the class that is returned to a client of the
packet driver spec in the driver_info call. The int_no is the
hardware interrupt number, defaults to 4 (COM1). The io_addr
is the hardware I/O address, defaults to 0x3f8 (COM1). The
baud_rate defaults to 4800 baud. The recv_buf_size defaults to
3000.
Errorlevels
Some of the packet drivers return error codes. Some of
these error codes indicate fatal errors, and some are merely
warnings. For the moment, you must consult the source to see
what the errorcodes mean. For example, pktchk returns 0 if a
packet driver exists at a given address, and 1 if not. You
might use it in a batch file that only installs a packet driver
if one is not found.
rem only install the packet driver if there isn't one
rem already.
pktchk 0x7e
if errorlevel 0 goto gotit
ni5210 0x7e
:gotit
The "errorlevel" test is true if the errorlevel is less
than or equal to the parameter.
Appendix A
Interrupt usage in the range 0x60 through 0x80, from Ralf
Brown's interrupt list.
60 -- -- reserved for user interrupt
60 -- -- FTP Driver - PC/TCP Packet Driver Specification
60 01 FF FTP Driver - DRIVER INFO
60 02 -- FTP Driver - ACCESS TYPE
60 03 -- FTP Driver - RELEASE TYPE
60 04 -- FTP Driver - SEND PACKET
60 05 -- FTP Driver - TERMINATE DRIVER FOR HANDLE
60 06 -- FTP Driver - GET ADDRESS
60 07 -- FTP Driver - RESET INTERFACE
60 11 -- 10-NET - LOCK AND WAIT
60 12 -- 10-NET - LOCK
60 13 -- 10-NET - UNLOCK
60 20 -- FTP Driver - SET RECEIVE MODE
60 21 -- FTP Driver - GET RECEIVE MODE
60 24 -- FTP Driver - GET STATISTICS
61 -- -- reserved for user interrupt
62 -- -- reserved for user interrupt
63 -- -- reserved for user interrupt
64 -- -- reserved for user interrupt
65 -- -- reserved for user interrupt
66 -- -- reserved for user interrupt
67 -- -- LIM EMS
...
67 DE 00 Virtual Control Program Interface - INSTALLATION CHECK
...
68 01 -- APPC/PC
...
69 -- -- unused
6A -- -- unused
6B -- -- unused
6C -- -- system resume vector (CONVERTIBLE)
6C -- -- DOS 3.2 Realtime Clock update
6D -- -- VGA - internal
6E -- -- unused
6F -- -- Novell NetWare - PCOX API (3270 PC terminal interface)
6F 00 -- 10-NET - LOGIN
...
70 -- -- IRQ8 - AT/XT286/PS50+ - REAL-TIME CLOCK
71 -- -- IRQ9 - AT/XT286/PS50+ - LAN ADAPTER 1
72 -- -- IRQ10 - AT/XT286/PS50+ - RESERVED
73 -- -- IRQ11 - AT/XT286/PS50+ - RESERVED
74 -- -- IRQ12 - PS50+ - MOUSE INTERRUPT
75 -- -- IRQ13 - AT/XT286/PS50+ - 80287 ERROR
76 -- -- IRQ14 - AT/XT286/PS50+ - FIXED DISK
77 -- -- IRQ15 - AT/XT286/PS50+ - RESERVED
78 -- -- not used
79 -- -- not used
7A -- -- Novell NetWare - LOW-LEVEL API
7A -- -- AutoCAD Device Interface
7B -- -- not used
7C -- -- not used
7D -- -- not used
7E -- -- not used
7F -- -- HDILOAD.EXE - 8514/A VIDEO CONTROLLER INTERFACE
7F -- -- HLLAPI (High-Level Language API)
80 -- -- reserved for BASIC